I wonder if the better UX is to simply do all of the includes all the time in get. I can't think of any use cases where making this configurable is strictly necessary.

I wonder if the better UX is to simply do all of the includes all the time in get. I can't think of any use cases where making this configurable is strictly necessary.

That sounds reasonable to me and fits my specific use case perfectly. I simply followed the Connect API where they're all optional.

I wonder if the better UX is to simply do all of the includes all the time in get. I can't think of any use cases where making this configurable is strictly necessary.

That sounds reasonable to me and fits my specific use case perfectly. I simply followed the Connect API where they're all optional.

@tdstein should I implement this change or do we need further discussion with others first?

I wonder if the better UX is to simply do all of the includes all the time in get. I can't think of any use cases where making this configurable is strictly necessary.

That sounds reasonable to me and fits my specific use case perfectly. I simply followed the Connect API where they're all optional.

@tdstein should I implement this change or do we need further discussion with others first?

Go for it. It should be just modifying the request to include the query arguments.

Go for it. It should be just modifying the request to include the query arguments.

@tdstein Done.

Note that CI cannot run integration tests from a fork due to security around secrets.

connect-1 | time="2025-06-25T21:29:05.292Z" level=warning msg="Unable to obtain a valid license: Your Posit Connect license has expired. Please contact your Customer Success representative or email sales@posit.co to obtain a current license."

Locally I ran 2025.03.0 and 2025.02.0 successfully, but preview fails a variety of other tests.

Note that CI cannot run integration tests from a fork due to security around secrets.

@cgraham-rs - since you are using a fork, you don't have access to the repository secrets. If you set the CONNECT_LICENSE environment variable in GitHub secrets, it should work on your branch.

Alternatively, you can recreate the pull request as a branch off of main. Either should work.

preview fails a variety of other tests.

I'm also seeing that. I'll address it in as a separate issue.

@cgraham-rs - here is a fix for the integration test failures: #417

Closing in favor of non-fork PR: #420